docs: clarify that release tags keep the leading v prefix#3463
Open
emrdgrmnci wants to merge 1 commit into
Open
docs: clarify that release tags keep the leading v prefix#3463emrdgrmnci wants to merge 1 commit into
emrdgrmnci wants to merge 1 commit into
Conversation
Readers were replacing vX.Y.Z with bare versions like 0.12.11, which fails because git tags are named v0.12.11. Assisted-by: Cursor Grok 4.5 (supervised) Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vwhen substituting release tags (e.g.v0.12.11, not0.12.11).couldn't find remote reffailure.Test plan
vX.Y.Z.uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@v0.12.11succeeds and@0.12.11fails.